Steps to convert a database from Access to SQL

SureSync provides the functionality to easily migrate from Access to SQL. You can also use the same set of steps to migrate back from SQL to Access if the need ever arises.

Steps to convert a database from Access to SQL

Go to File | Database | Copy.
Select “SQL/MSDE Database (*.mdf)” from the list.
In the “SQL Server Database Path (as seen by server)” field you need to enter the path where you want SureSync to create the SQL database file.
Enter the name of the SQL server or the SQL server instance name in the “Name of SQL Server” field. Please note that the “SQL Server Database Path” field is from the perspective of the machine listed here. For example, in the screenshot the "C:\Databases\" directory must exist on the local SureSync machine for the database to be able to be created. If a server named SQLSvr1 was listed in 'Name of SQL Server' then the C:\Databases path would have to exist on that machine before the upgrade can take place.
In the “Name of SQL Database” field you should enter the name of the database. It is recommend that this be left at SureSync.
Click the continue button and the copy process will start. This can be a lengthy process depending on the size of the original database.

Some Notes On SQL

SureSync supports SQL 2000, 2005 and 2008 server editions, SQL Server 2005 Express Edition, SQL Server Express 2008, and the MSDE engine. The SQL Server 2005 Express Edition, SQL Server 2008 Express Edition and MSDE engine are all free downloads which can be obtained from Microsoft's SQL Web Site.
Your SQL server must be running either Windows Integrated Security or Mixed Security. SQL only security is not supported. If your SQL server is running SQL only security you will need to use the MSDE engine, SQL Server 2005 Express Edition or SQL Server 2008 Express Edition on the machine where SureSync is installed.
The account, which SureSync is running under, must have permissions to create a database on the SQL server and permissions to access that database. Please contact your SQL server administrator for assistance with this.